* taken from archiched messages around sept 2004



02 MEM PROTECT - Switch INTERNAL to OFF
04 MIDI CHANNEL - Set midi channel to channel of data [mostly channel 1]
05 MIDI DATA - Switch ECLUSIVE to ENA [enabled]
03 SAVE/LOAD - LOAD/SAVE > MIDI > [data type] > YES, YES

Note: It seems that data type must be matched. In order to
sucessfully load data that was stored as Voice + Op-Mem data, I had
to set up the VZ to accept that type of data.



******************************
known vz file-extensions:

VZeditor on Atari uses:
*.VZT for a tone
*.VZB for a Bank
*.VZ8 for a Block (8 voices)


VZeditor on PC uses:
*.VZV for a tone
*.VZ1 for a Bank

*******************************




*Here are the error messages I have been getting when sending VZ sysex
data to the VZ-8m. (See my previous message about channel and data
type matching.)
---------------------------------------------------------------
Message: --TRANS ERROR--- | CHECK SYSTEM!
Problem: Data channel <> VZ receive channel
Solution: Change VZ channel to match sysex file data.

Message: --MIDI ERROR--- | RECEIVE ERROR
Problem: Data type transmitted <> Data type expected
Solution: Select proper data type when loading data type into VZ.
---------------------------------------------------------------
To see the channel and size of data, you can use debug [PC].

EXAMPLE [VZCard9.syx]:
F0 44 03 00 70 70 02 F7
F0 = system exclusive data coming
44 = Casio product ID
03 = VZ line
00 = VZ-1 format data [02 = VZ-8m format data]
70 = channel 1 [7N where N = 0->F meaningchannels 1->16]
70 = open communication
02 = INT 64 voices + 64 op-mems
F7 = end of sysex transmission.

F0 44 03 00 70 74 . . . [data] . . . F7
74 = data is coming next

other codes for the 6th byte:
71 = close
72 = ok
73 = error
---------------------------------------------------------------
For the VZ-8m, I have the following SYSEX data sizes [received from
VZ]:

65661 = FULL [Voice + Op-Men + Total]
65644 = VC+OP [Voice + Op-Mem]
43094 = VOICE
22672 = OPMEM

The VZ files posted in files are 55958 which I assume is the VZ-1/VZ-
10M VC+OP size.
---------------------------------------------------------------





*I had strange problems with midi-ox running on windows xp and older synth, like kawai k5 and casio vz10. now i use soundquest editor for transfers and as a libarian. It sucks as an editor - i use dr.Ts editors on atari instead!





* Hi! I remember some people also have problems with that Windows based
Editor on newer Systems like XP. If you just want to transfer
soundbanks you can use Vzdump on a atari (emulator). I just tried it,
and it works. All i had to do is changing the filename extension into
VZdump language...

I found the info at http://casio.sallyandsteve.com/

" Atari ST Software
VZDUMP2.PRG, and its resource file VZDUMP.RSC have been donated by
Fred Fee. They are a CASIO VZ utility programme for the Atari ST. This
is what Fred says about it:

"I have a MIDI dump program for the Atari that can handle data in X-Or
format from any of the VZ series, so that data can be swapped freely
between them. I used it to load files from the EasyVeeZee site since
they are in X-Or VZ1 VC+OP format and then loaded the voices into my
VZ8M. I also used the program to save my VZ8M bank in VZ1 format.
Steve's editor uses the .VZ1 extension whereas my program uses .VZB
for VC+OP banks from the VZ1 since I made it compatible with the
nomenclature used by X-Or."Thanks Fred. "



*Footnotes:

VZ-8m data transfer VZ-1/10m data first then VZ-8m specific data. So,
if someone tried to send VZ-8m data to a VZ-1/10m, the voice and op-
mem data should load.

Here's the dump sequence:

F0 44 03 00 7A 70 02 F7
[open communication for 64 voices and 64 op-mems on channel 11]

F0 44 03 00 7A 74 . . . [data] F7
[VZ-1/10m common data on channel 11]

F0 44 03 00 7A 71 F7
[close communication on channel 11]

F0 44 03 02 7A 70 03 F7
[open communication for 64 voices, 64 op-mems, and TOTAL CONTROL on
channel 11]

F0 44 03 02 7A 74 . . . [data] F7
[VZ-8m specific data on channel 11]

F0 44 03 02 7A 71 F7
[close communication on channel 11]

The first 3 sysex commands should be understood by all VZ. The last 3
should be ignored by all VZs except the VZ-8m.

Hope this helps.



*At this point you probably don't need to use debug, unless you just
want to take a look at some sysex files.

Debug came with MS-DOS and is still part of windows. It is a simple
utility.

I recommend saving a copy of the sysex files you will be looking at
to a folder in your root directory. I usually create C:\temp and
copy the files there. Then:

(1) From Windows Start, click Run, type: command
This should take you to a C: prompt in a dos window.

(2) Change the prompt to wherever the files are using the cd command
(for change directory).
I type cd c:/temp

(3) At C:\temp dir *.syx will list the sysex files you have placed
there.

(4) Type debug vzcard9.syx [for example]

(5) Type d 100 <enter> to start displaying the data. Type d <enter>
to see another block of data.

Other debug commands:
? = list of debug commands
q = quit [then type exit to close the dos window]
n = name
EXAMPLE: n vzcard8.syx
l = load
s = search
EXAMPLE: s 100 ffff f0 44 03
d = display
EXAMPLE: d db8f

I highly recommend not changing anything around with debug unless you
know what you are doing. In other words, don't use the fill or enter
commands without knowing first what you are changing.




* MidiOX is freeware, and it works great with any synth i have.
http://www.midiox.com/
It also shows you the sysex code - so maybe there is no need to do
this debug thing in windows!




::::
Hope this helps.